TB

Trezor Bridge

Secure & Smooth Crypto Access — local bridge for Trezor devices

Local • Private • Trusted

Bridge your browser and apps to your Trezor — safely and privately.

Trezor Bridge is a lightweight local service that enables secure communication between web or desktop applications and your connected Trezor hardware wallet. It keeps all key material on-device, requires user confirmation for every signing operation, and avoids routing sensitive data through third‑party servers.

Privacy-first

Runs locally on your machine — Bridge does not relay data through remote servers. Requests are forwarded only after origin checks and user approval.

Verified signing

The Trezor device displays transaction details for manual confirmation. Only approved operations produce signatures.

Cross-platform

Installers for Windows, macOS, and Linux. Bridge auto-starts when needed and supports seamless updates.

Developer-friendly

Local APIs and examples enable secure integrations for wallets, dApps, and tooling.

How it works

Your web page or desktop app sends a request to the Bridge service running locally.
Bridge validates the request origin and forwards it to the connected Trezor device.
The device shows transaction details and asks for your physical confirmation.
After approval, the device signs locally and Bridge returns the signed payload to the originating app for broadcast.

Bridge never stores private keys — all signing occurs inside the Trezor device.

Developer integration

Trezor Bridge exposes a minimal local API that lets applications request device operations while preserving origin checks and requiring explicit user confirmation. Developers should follow these principles:

Request only the minimum required scopes and data from users.
Display clear UI prompts describing the action and guide users to verify details on their device.
Use short-lived sessions and avoid storing signed payloads unnecessarily.
Validate the calling origin and ensure TLS for web-based integrations.

// Example (conceptual): request signing via local Bridge API fetch('http://localhost:21325/sign', { method: 'POST', body: JSON.stringify({ tx: ... }), headers: { 'Origin': 'https://example.com' } })

Security recommendations

Always download Bridge from the official Trezor site and verify package authenticity when provided.
Keep your Trezor firmware up to date — firmware updates include security patches and compatibility fixes.
Verify all addresses and amounts on the physical device before approving any transaction.
Run Bridge only on personal machines you trust; avoid using public or shared systems for signing operations.

Troubleshooting

Check cable & power: ensure the USB cable is securely connected and the device is unlocked.
Restart Bridge: look for the Bridge icon in the system tray/taskbar and restart the service.
Browser permissions: confirm your browser allows local socket communication to Bridge.
Reinstall: if problems persist, reinstall Bridge from the official site and reboot your machine.

Privacy & data handling

Bridge is intentionally lightweight and local — it does not collect or transmit personal data to Trezor servers. Diagnostic logs (if shared) should be reviewed to remove sensitive content before being sent to support.

Resources & support

For downloads, documentation, and support, visit the official Trezor resources:

TB

Trezor Bridge

Secure & Smooth Crypto Access — local bridge for Trezor devices

Local • Private • Trusted

Bridge your browser and apps to your Trezor — safely and privately.

Trezor Bridge is a lightweight local service that enables secure communication between web or desktop applications and your connected Trezor hardware wallet. It keeps all key material on-device, requires user confirmation for every signing operation, and avoids routing sensitive data through third‑party servers.

Privacy-first

Runs locally on your machine — Bridge does not relay data through remote servers. Requests are forwarded only after origin checks and user approval.

Verified signing

The Trezor device displays transaction details for manual confirmation. Only approved operations produce signatures.

Cross-platform

Installers for Windows, macOS, and Linux. Bridge auto-starts when needed and supports seamless updates.

Developer-friendly

Local APIs and examples enable secure integrations for wallets, dApps, and tooling.

How it works

Your web page or desktop app sends a request to the Bridge service running locally.
Bridge validates the request origin and forwards it to the connected Trezor device.
The device shows transaction details and asks for your physical confirmation.
After approval, the device signs locally and Bridge returns the signed payload to the originating app for broadcast.

Bridge never stores private keys — all signing occurs inside the Trezor device.

Developer integration

Trezor Bridge exposes a minimal local API that lets applications request device operations while preserving origin checks and requiring explicit user confirmation. Developers should follow these principles:

Request only the minimum required scopes and data from users.
Display clear UI prompts describing the action and guide users to verify details on their device.
Use short-lived sessions and avoid storing signed payloads unnecessarily.
Validate the calling origin and ensure TLS for web-based integrations.

// Example (conceptual): request signing via local Bridge API fetch('http://localhost:21325/sign', { method: 'POST', body: JSON.stringify({ tx: ... }), headers: { 'Origin': 'https://example.com' } })

Security recommendations

Always download Bridge from the official Trezor site and verify package authenticity when provided.
Keep your Trezor firmware up to date — firmware updates include security patches and compatibility fixes.
Verify all addresses and amounts on the physical device before approving any transaction.
Run Bridge only on personal machines you trust; avoid using public or shared systems for signing operations.

Troubleshooting

Check cable & power: ensure the USB cable is securely connected and the device is unlocked.
Restart Bridge: look for the Bridge icon in the system tray/taskbar and restart the service.
Browser permissions: confirm your browser allows local socket communication to Bridge.
Reinstall: if problems persist, reinstall Bridge from the official site and reboot your machine.

Privacy & data handling

Bridge is intentionally lightweight and local — it does not collect or transmit personal data to Trezor servers. Diagnostic logs (if shared) should be reviewed to remove sensitive content before being sent to support.

Resources & support

For downloads, documentation, and support, visit the official Trezor resources:

TB

Trezor Bridge

Secure & Smooth Crypto Access — local bridge for Trezor devices

Local • Private • Trusted

Bridge your browser and apps to your Trezor — safely and privately.

Trezor Bridge is a lightweight local service that enables secure communication between web or desktop applications and your connected Trezor hardware wallet. It keeps all key material on-device, requires user confirmation for every signing operation, and avoids routing sensitive data through third‑party servers.

Privacy-first

Runs locally on your machine — Bridge does not relay data through remote servers. Requests are forwarded only after origin checks and user approval.

Verified signing

The Trezor device displays transaction details for manual confirmation. Only approved operations produce signatures.

Cross-platform

Installers for Windows, macOS, and Linux. Bridge auto-starts when needed and supports seamless updates.

Developer-friendly

Local APIs and examples enable secure integrations for wallets, dApps, and tooling.

How it works

Your web page or desktop app sends a request to the Bridge service running locally.
Bridge validates the request origin and forwards it to the connected Trezor device.
The device shows transaction details and asks for your physical confirmation.
After approval, the device signs locally and Bridge returns the signed payload to the originating app for broadcast.

Bridge never stores private keys — all signing occurs inside the Trezor device.

Developer integration

Trezor Bridge exposes a minimal local API that lets applications request device operations while preserving origin checks and requiring explicit user confirmation. Developers should follow these principles:

Request only the minimum required scopes and data from users.
Display clear UI prompts describing the action and guide users to verify details on their device.
Use short-lived sessions and avoid storing signed payloads unnecessarily.
Validate the calling origin and ensure TLS for web-based integrations.

// Example (conceptual): request signing via local Bridge API fetch('http://localhost:21325/sign', { method: 'POST', body: JSON.stringify({ tx: ... }), headers: { 'Origin': 'https://example.com' } })

Security recommendations

Always download Bridge from the official Trezor site and verify package authenticity when provided.
Keep your Trezor firmware up to date — firmware updates include security patches and compatibility fixes.
Verify all addresses and amounts on the physical device before approving any transaction.
Run Bridge only on personal machines you trust; avoid using public or shared systems for signing operations.

Troubleshooting

Check cable & power: ensure the USB cable is securely connected and the device is unlocked.
Restart Bridge: look for the Bridge icon in the system tray/taskbar and restart the service.
Browser permissions: confirm your browser allows local socket communication to Bridge.
Reinstall: if problems persist, reinstall Bridge from the official site and reboot your machine.

Privacy & data handling

Bridge is intentionally lightweight and local — it does not collect or transmit personal data to Trezor servers. Diagnostic logs (if shared) should be reviewed to remove sensitive content before being sent to support.

Resources & support

For downloads, documentation, and support, visit the official Trezor resources:

TB

Trezor Bridge

Secure & Smooth Crypto Access — local bridge for Trezor devices

Local • Private • Trusted

Bridge your browser and apps to your Trezor — safely and privately.

Trezor Bridge is a lightweight local service that enables secure communication between web or desktop applications and your connected Trezor hardware wallet. It keeps all key material on-device, requires user confirmation for every signing operation, and avoids routing sensitive data through third‑party servers.

Privacy-first

Runs locally on your machine — Bridge does not relay data through remote servers. Requests are forwarded only after origin checks and user approval.

Verified signing

The Trezor device displays transaction details for manual confirmation. Only approved operations produce signatures.

Cross-platform

Installers for Windows, macOS, and Linux. Bridge auto-starts when needed and supports seamless updates.

Developer-friendly

Local APIs and examples enable secure integrations for wallets, dApps, and tooling.

How it works

Your web page or desktop app sends a request to the Bridge service running locally.
Bridge validates the request origin and forwards it to the connected Trezor device.
The device shows transaction details and asks for your physical confirmation.
After approval, the device signs locally and Bridge returns the signed payload to the originating app for broadcast.

Bridge never stores private keys — all signing occurs inside the Trezor device.

Developer integration

Trezor Bridge exposes a minimal local API that lets applications request device operations while preserving origin checks and requiring explicit user confirmation. Developers should follow these principles:

Request only the minimum required scopes and data from users.
Display clear UI prompts describing the action and guide users to verify details on their device.
Use short-lived sessions and avoid storing signed payloads unnecessarily.
Validate the calling origin and ensure TLS for web-based integrations.

// Example (conceptual): request signing via local Bridge API fetch('http://localhost:21325/sign', { method: 'POST', body: JSON.stringify({ tx: ... }), headers: { 'Origin': 'https://example.com' } })

Security recommendations

Always download Bridge from the official Trezor site and verify package authenticity when provided.
Keep your Trezor firmware up to date — firmware updates include security patches and compatibility fixes.
Verify all addresses and amounts on the physical device before approving any transaction.
Run Bridge only on personal machines you trust; avoid using public or shared systems for signing operations.

Troubleshooting

Check cable & power: ensure the USB cable is securely connected and the device is unlocked.
Restart Bridge: look for the Bridge icon in the system tray/taskbar and restart the service.
Browser permissions: confirm your browser allows local socket communication to Bridge.
Reinstall: if problems persist, reinstall Bridge from the official site and reboot your machine.

Privacy & data handling

Bridge is intentionally lightweight and local — it does not collect or transmit personal data to Trezor servers. Diagnostic logs (if shared) should be reviewed to remove sensitive content before being sent to support.

Resources & support

For downloads, documentation, and support, visit the official Trezor resources: